Skip to main content

This is a new service – your feedback will help us to improve it.

Royal Borough of Kensington and Chelsea

Article 4 direction area

There is a problem

  • 84 issue of type invalid category value

Article 4 - No 59

reference
33
name
Article 4 - No 59
article-4-direction
33
permitted-development-rights

undefined

Minor alterations in Conservation Areas
uprns
address-texts
geometry
MULTIPOLYGON (((-0.197910 51.500590,-0.197340 51.500790,-0.197500 51.500950,-0.197520 51.500980,-0.198100 51.500770,-0.197930 51.500590,-0.197930 51.500580,-0.197910 51.500590)),((-0.197440 51.501130,-0.197100 51.501260,-0.196970 51.501300,-0.197080 51.501410,-0.197170 51.501520,-0.197320 51.501680,-0.197450 51.501630,-0.197730 51.501540,-0.197550 51.501350,-0.197720 51.501280,-0.197550 51.501090,-0.197440 51.501130)),((-0.198270 51.501250,-0.198330 51.501320,-0.198620 51.501220,-0.198870 51.501120,-0.198890 51.501120,-0.198890 51.501110,-0.198900 51.501110,-0.198900 51.501090,-0.198590 51.500750,-0.198570 51.500750,-0.198570 51.500740,-0.198540 51.500740,-0.198530 51.500750,-0.198400 51.500790,-0.198250 51.500850,-0.197780 51.501010,-0.197690 51.501050,-0.197670 51.501050,-0.197770 51.501170,-0.197810 51.501200,-0.197840 51.501240,-0.197860 51.501240,-0.197950 51.501200,-0.198160 51.501130,-0.198270 51.501250)))
point
POINT (-0.197913 51.501101)
notes
entry-date
2025-01-03
start-date
end-date

How to fix this issue

Your dataset is missing the permitted-development-rights column.

The Article 4 direction area guidance explains how to fix the issue:

permitted-development-rights

A list of the permitted development rights withdrawn by the article 4 direction.

Separate the rights in the list using semicolons.

Only use rights from our permitted development right dataset. If the area withdraws a permitted development right that is not in our dataset, email digitalland@communities.gov.uk.

Example: 3D;3M;11B

How to improve Royal Borough of Kensington and Chelsea’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL